@scottalanmiller said:

So this interesting. We have our first desktop added into InTune that is running Windows 10 Tech Preview. In InTune it does not display as "Windows 10" as I would have expected. Instead it displays as "Windows 6.4" which is slightly confusing as the kernel is "NT 6.4" and the name is "Windows 10." Blending the two is odd.

Just found it interesting.

I've seen this behavior before - I think it was WSUS - windows 8(.1) was reported by something than it's normal name.

Bind error is found when a client does a dcdiag to the server.

@Dominica said:

Still having a number of challenges getting very basic things to work.

Such as?

@Mike-Ralston said:

@Dashrender said:

If you are booting from UEFI mode (not legacy mode), you must use FAT32 as UEFI won't boot from NTFS.

I haven't had this issue, I can boot from UEFI into a NTFS configured drive. Possibly a special UEFI designed around that, I have no idea.

Exactly.

The UEFI specification explicitly requires support for FAT32 for EFI System partitions (ESPs), and FAT16 or FAT12 for removable media;[20]:section 12.3 specific implementations may support other file systems.

http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Disk_device_compatibility

@scottalanmiller said:

@thecreativeone91 said:

The preview isn't usually open to as many people like it is for Windows 10 though.

What part of this is confusing? I have no idea how you are struggling with this sentence.

It simply says that the Windows 10's preview is open to more people than previews are usually open to.

That wording made sense. His just isn't registering with me.